Skip to content

post processing: check for finding being None#12713

Merged
Maffooch merged 1 commit into
DefectDojo:bugfixfrom
valentijnscholten:celery-post-process-check-None
Jun 30, 2025
Merged

post processing: check for finding being None#12713
Maffooch merged 1 commit into
DefectDojo:bugfixfrom
valentijnscholten:celery-post-process-check-None

Conversation

@valentijnscholten

Copy link
Copy Markdown
Member

Fixes #11958

Sometimes during unit tests we see that the finding is already deleted once the post_process_finding_save is being executed.
This can also happen in real life if a finding is deleted manually or by the duplicate delete job.
This PR add a check so that the logs aren't polluted with stacktraces. There is still logging at the warning level as it's not 100% expected/intended to have this happening.

@valentijnscholten valentijnscholten added this to the 2.48.0 milestone Jun 28, 2025
@dryrunsecurity

Copy link
Copy Markdown

DryRun Security

No security concerns detected in this pull request.


All finding details can be found in the DryRun Security Dashboard.

@valentijnscholten valentijnscholten changed the title post processing: check for finding==None post processing: check for finding being None Jun 28, 2025

@mtesauro mtesauro left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@Maffooch Maffooch requested review from dogboat and hblankenship June 30, 2025 15:05
@Maffooch Maffooch merged commit bccd795 into DefectDojo:bugfix Jun 30, 2025
77 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants